Competence is not what you know. It is what you are willing to share

There is a quiet shift underway in fire engineering. It is not about new guidance, new tools or even new regulation. It is about something less comfortable: whether the profession is prepared to learn in public.

The introduction of mandatory occurrence reporting (MOR) has, rightly, focused attention on accountability. Certain events must now be reported. Thresholds are defined. The regulator is informed. That is progress.

But it is not, on its own, a learning system.

The more interesting question sits alongside it. What happens to everything that does not quite meet the threshold? The near misses. The uneasy details. The design assumptions that felt stretched at the time. The product that did not behave quite as expected. The inconsistency between what was drawn and what was built.

That is where voluntary occurrence reporting sits, and it is far more important than it is often treated.

Your paper makes the point clearly: a system based only on mandatory reporting will always be reactive. It captures events once they are serious enough, visible enough, or defined clearly enough to require escalation. It does not capture the weak signals.

Those weak signals are where most of the real risk sits.

Voluntary reporting, particularly through systems like CROSS, does something fundamentally different. It allows practitioners to surface uncertainty, pattern and concern before they crystallise into failure. It turns isolated experience into shared intelligence. And it does so in a way that protects the individual while benefiting the profession.

But only if people use it.

That is the uncomfortable part. The barrier has never really been the absence of systems. It has been culture. Concerns about liability, reputation, commercial sensitivity. A tendency to resolve issues quietly rather than expose them, even in anonymised form.

The result is predictable. Lessons are learned locally and lost globally. The same issues reappear, dressed slightly differently, on another project.

We should be honest about what that represents. Not a lack of competence in the traditional sense, but a limitation in how competence is exercised.

Because competence is not just qualification, experience or accreditation. It is awareness. It is judgement. And it is engagement with the wider evidence base of the profession.

If you are not exposed to the patterns emerging across the industry, your judgement is narrower than it needs to be. If you are not contributing to that shared picture, you are relying on others to do it for you.

There is also a more strategic point here. The post-Grenfell regime risks becoming overly centred on compliance. MOR will be measured, audited and enforced. That is necessary. But compliance systems do not, by themselves, create insight.

Insight comes from aggregation. From pattern recognition. From connecting issues that, in isolation, do not look significant.

That is precisely what voluntary reporting enables.

The direction of travel is clear. Fire engineering is moving, slowly but deliberately, from a compliance-driven discipline to a learning-based one. From asking “have we met the requirement?” to asking “what are we missing?”

Voluntary occurrence reporting sits at the centre of that shift.

The mechanisms now exist. Confidentiality is protected. The platform is established. The outputs are there to be read and used.

The question is no longer whether the system works.

It is whether we are prepared to participate in it.

This is a general professional reflection, not project-specific advice. But if competence is part of your professional identity, it is worth asking a slightly sharper question than usual. Not just “what have I learned?”, but “what have I shared?”